Restful method and apparatus to import content by geo-aware content caching service

ABSTRACT

Representational state transfer (REST) based geo-aware content transfer includes a REST server configured for receiving an application programming interface (API) request from a client device. The REST server obtains a upload universal resource locator (URL) targeting a caching server that is geographically closest to the client device, constructs an upload link containing the upload URL and a completion callback, and sends the upload link to the client device. The client device uses the upload URL to upload content to the caching server. The caching server interprets the completion callback to obtain a completion URL and, upon completion of content uploading, makes a REST API call using the completion URL. Responsive to the REST API call, the REST server executes an inbound operation to complete the uploading to a content management system and returns the content URL to the caching server which sends the content URL to the client device.

CROSS-REFERENCE TO RELATED APPLICATION(S)

This application claims a benefit of priority under 35 U.S.C. § 119(e)from U.S. Provisional Application No. 62/507,325, filed May 17, 2017,entitled “RESTFUL METHOD AND APPARATUS TO IMPORT CONTENT BY GEO-AWARECONTENT CACHING SERVICE,” which is fully incorporated by referenceherein for all purposes.

TECHNICAL FIELD

This disclosure relates generally to managing content in a networkcomputing environment. More particularly, this disclosure relates totransferring content in the context of a network-based contentmanagement system. Even more particularly, this disclosure relates to atechnical solution that supports geo-aware content upload with a RESTfulAPI so that the content can be properly imported into a contentrepository of a content management system at the backend of anenterprise computing environment.

BACKGROUND OF THE RELATED ART

Content transfer in a content management system refers to the means ofuploading or downloading content files between a client machine and acontent server for the associated document objects. A content managementsystem usually provides various application programming interfaces(APIs) to enable content transfer, by socket APIs or Web Services, forexample. For an organization that has deployed a content managementsystem in its centralized data center and that, at the same time, has anumber of large branch offices world-wide, it becomes a challenge forall branch offices to transfer large content files to the centralizedcontent management system stably and efficiently.

SUMMARY OF THE DISCLOSURE

A content management system operating in an enterprise computingenvironment (e.g., a private network of an enterprise, also referred toas a local area network or LAN) can utilize a caching server configuredfor providing branching office content services (BOCS) to client deviceson the private network. The caching server (referred to hereinafter“BOOS server”) can help to transfer content locally on the privatenetwork (e.g., to and from a content repository of the contentmanagement system) in a synchronous or asynchronous mode and providegeo-aware content upload and download services over the HypertextTransfer Protocol (HTTP).

For example, when a client needs to create a document in the contentmanagement system, the system first creates a document object forcapturing metadata associated with the document and then uploads thedocument thus created to its adjacent BOOS server. In this way, thecontent upload process can leverage the benefit of a LAN or edgenetwork. The BOOS server can upload the document to a content server atthe backend of the LAN asynchronously using its private communicationchannel with the content server. FIG. 1 depicts an example of thisstandalone content caching service solution (100).

As illustrated in FIG. 1, the standalone content caching servicesolution requires a thick client (101 a, . . . , 101 n) to be installedon the client machine's operating system (OS), where the thick clientspawns a separate process to upload the content in the background via aBOOS server (120 a, . . . , 120 n) to a content server (150) by way ofremote procedure calls (RPC) or web services provided by a web server(110). The thick client cannot be deployed on a middleware server andthe web server is required to install an agent (111). The agent runningon the web server communicates with the thick client to start and reportprogress on the content transfer. This web server agent is stateful (andhence requires a “sticky” session). Therefore, this solution does notsupport failover in High Availability (HA) environment. Failover can beimportant in critical applications where it is important that userscontinue to have access to an application even if components of theapplication fail.

Embodiments disclosed herein provide a new technical solution thatsupports representational state transfer (REST) based geo-aware contentupload without requiring any thick client be installed on a clientmachine. The differences lie not only in the API format, but also in therequirements for client and server deployment. FIG. 2 depicts an exampleof a new RESTful API-based geo-aware content caching service solution(200) in the context of a network topology. The term “REST” refers tothe representational state transfer technology or software architecture,while the term “RESTful” can be used to describe a system, software, orservice that implements the REST technology or architecture. The term“RESTful API” is used interchangeably with “REST API” and can refer to aRESTful web service or a set of RESTful web services.

As illustrated in FIG. 2, the new solution provides REST services (230)for a “lite” client (201 a, . . . , 201 n) to create documents, and hasenhanced/advanced BOOS servers (220 a, . . . , 220 n) that can interactwith a REST server (210) using a stateless protocol to store thedocuments in a content server (250) operating at the backend of aprivate network (290). In the example of FIG. 2, the thin clients aredistributed (e.g., in edge networks 280 a, . . . , 280 n) and remotefrom the content server, which resides in a separate LAN (270). On theclient side, any HTTP client can be used to upload the content, with nodependency on the client OS or client application framework.

In some embodiments, a REST server receives REST API request from aclient device for an upload link, the REST API request containing anetwork location associated with the client device. In response, theREST server obtains a upload universal resource locator (URL) targetinga caching server that is geographically closest to the client device,constructs an upload link containing the upload URL and a completioncallback parameter, and sends the upload link to the client device.

The client device uses the upload URL in the upload link to uploadcontent to the caching server. In response, the caching serverinterprets the completion callback parameter in the upload link toobtain a completion URL and, upon completion of the uploading of thecontent from the client device, makes a REST API call to the REST serverusing the completion URL.

Responsive to the REST API call by the caching server, the REST serverexecutes an inbound operation to complete the uploading to a contentmanagement system. In some embodiments, the inbound operation includesassociating the content with a content URL in the content managementsystem. The REST server returns the content URL to the caching serverwhich, in turn, sends the content URL to the client device.

In one embodiment, a system may comprise a processor, a non-transitorycomputer-readable storage medium, and stored instructions translatableby the processor to implement a workflow that can complete a contentupload using the method substantially as described herein. Anotherembodiment comprises a computer program product having a non-transitorycomputer-readable storage medium storing instructions translatable by aprocessor to perform a method substantially as described herein.Numerous other embodiments are also possible.

Embodiments disclosed herein can provide many advantages. For example,the new solution does not require the installation of a thick client ona client machine's OS, will work with any HTTP client, and does notutilize a server-side agent so that the REST server can remainstateless.

These, and other, aspects of the disclosure will be better appreciatedand understood when considered in conjunction with the followingdescription and the accompanying drawings. It should be understood,however, that the following description, while indicating variousembodiments of the disclosure and numerous specific details thereof, isgiven by way of illustration and not of limitation. Many substitutions,modifications, additions, and/or rearrangements may be made within thescope of the disclosure without departing from the spirit thereof, andthe disclosure includes all such substitutions, modifications,additions, and/or rearrangements.

BRIEF DESCRIPTION OF THE DRAWINGS

The drawings accompanying and forming part of this specification areincluded to depict certain aspects of the invention. A clearerimpression of the invention, and of the components and operation ofsystems provided with the invention, will become more readily apparentby referring to the exemplary, and therefore non-limiting, embodimentsillustrated in the drawings, wherein identical reference numeralsdesignate the same components. Note that the features illustrated in thedrawings are not necessarily drawn to scale.

FIG. 1 depicts a diagrammatic representation of an example of astandalone content caching service solution in a computer networkenvironment.

FIG. 2 depicts a diagrammatic representation of an example of a new andimproved REST based geo-aware content caching service solution in thecontext of a network topology according to some embodiments.

FIG. 3 depicts a diagrammatic representation of example operation of thestandalone content caching service solution of FIG. 1.

FIG. 4 depicts a diagrammatic representation of example operation of theREST based geo-aware content caching service solution of FIG. 2according to some embodiments.

FIG. 5 depicts a diagrammatic representation of an example of a workflowthat can complete a content upload using the REST based geo-awarecontent caching service solution of FIG. 2 according to someembodiments.

FIG. 6 depicts a diagrammatic representation of an example format of atoken generated by a REST server for internal consumption according tosome embodiments.

FIG. 7 depicts a diagrammatic representation of an example of a dataprocessing device that may be used to implement a client or servermachine according to some embodiments.

DETAILED DESCRIPTION

The invention and the various features and advantageous details thereofare explained more fully with reference to the non-limiting embodimentsthat are illustrated in the accompanying drawings and detailed in thefollowing description. Descriptions of well-known starting materials,processing techniques, components, and equipment are omitted so as notto unnecessarily obscure the invention in detail. It should beunderstood, however, that the detailed description and the specificexamples, while indicating some embodiments of the invention, are givenby way of illustration only and not by way of limitation. Varioussubstitutions, modifications, additions, and/or rearrangements withinthe spirit and/or scope of the underlying inventive concept will becomeapparent to those skilled in the art from this disclosure.

FIG. 3 depicts a diagrammatic representation of example operation of thestandalone content caching service solution of FIG. 1. In this example,enterprise computing environment (e.g., private network 300) can includebackend 310 (e.g., LAN 370), middleware 320, local area 330, andfrontend 340 (e.g., client device 301). Backend 310 may include contentserver 350, accelerated content services (ACS) server 355, storage 357,and database 360. Content server 350 may implement a content managementsystem. OpenText™ Documentum™ is an example of a content managementsystem suitable for enterprise content management (ECM).

In ECM, content transfer can involve large files (e.g., tens or hundredsof megabytes). Trying to upload such large files to a content server ina private network can be very difficult and complex. To this end, a webcomponent (e.g., ACS server 355) may be utilized to provide HTTP directcontent transfer for data objects. For example, ACS server 355 canfacilitate HTTP direct content transfer to storage 357 managed bycontent server 350, for instance, using database 360.

Accordingly, the standalone content caching service solution shown inFIG. 3 allows for HTTP direct content transfer. However, this HTTPdirect content transfer requires middleware 320 which, in this example,includes unified client facilities (UCF) server 322 and content serverclasses (e.g., Documentum Foundation Classes (DFC)) web services 324.UCF server 322 refers to a one-client-to-one-server component configuredfor orchestrating content transfer between UCF client 302 and forcontent server 350. DFC web services 324 implement a Java client withRPC communications to content server 350 for synchronous contenttransfer.

Content binaries can be transferred in various ways: for instance, usingweb services that leverage the integration of DFC 324, UCF server 322,and UCF client 302; using DFC API (Java) to upload from client device301 (e.g., a file stored in file system 304 can be communicated to DFCAPI through desktop program 306), to DFC 324, to content server 350,then to storage 370, or vice versa for downloading; or using ACS server355, DFC 324, UCF server 322, BOOS server, 335 UCF client 302 to uploada file from file system 304 through desktop program 306 and ACS server355 to storage 357, or to download a file from storage 357 through ACSserver 355 to desktop program 306 on client device 301. Another way todownload a file from storage 370 to desktop program 306 is through ACSserver 355 (or BOOS server 335).

Using ACS server 355 and/or BOOS server 335 can significantly acceleratecontent transfer. However, as illustrated in FIG. 3, this standalonecontent caching service solution requires UCF server 322 (as middleware320) and UCF client 302 (on client device 301) if a file is uploaded toACS server 355 or BOOS server 335.

UCF server 322 and UCF client 302 are designed for content transferorchestration. The UCF server component (e.g., UCF server 322) isdeployed along with DFC (e.g., DFC web services 324) in applicationservers. The UCF client component (e.g., UCF client 302) is usuallydeployed as a Java applet or .NET ActiveX plugins to run on an enduser's desktop machine (e.g., client device 301). Security concerns mayexist as this deployment scenario depends on security technologiesimplemented on the client device. Generally, UCF components are notsupported on mobile devices.

Once a UCF connection is set up between a UCF server and a UCF client,the UCF client must route to the same UCF server for all thecommunications. This is referred to as “sticky” sessions as the UCFclient must stick to the same UCF server. Sticky sessions also do notsupport HA environment (e.g., a server cluster of systems that aredurable and can operate continuously without failure for a long time,useful for fault tolerant, load balancing, speed, etc.). Sticky sessionsdo not support stateless scaling.

In computing, a stateless protocol refers to a communications protocolthat treats each request as an independent transaction that is unrelatedto any previous request so that the communication consists ofindependent pairs of request and response. A stateless protocol does notrequire the server to retain session information or status about eachcommunications partner for the duration of multiple requests (and henceis “stateless”). In contrast, a protocol that requires keeping of theinternal state on the server is referred to as a stateful protocol.Skilled artisans understand that stateless is one of the architecturalconstraints of a REST architecture. REST or RESTful web services are oneway of providing interoperability between computer systems on theInternet. REST-compliant web services allow requesting systems to accessand manipulate textual representations of web resources using a uniformand predefined set of stateless operations.

Leveraging the REST architecture, this disclosure provides systems,methods, and apparatuses for importing (or uploading, from theperspective of a client) content via RESTful geo-aware content cachingservices. In some embodiments, a REST server provides REST services fora client to create documents. The REST server interacts withenhanced/advanced BOOS servers via a stateless protocol, allowing acontent upload workflow to be completed using a REST API.

FIG. 4 depicts a diagrammatic representation of example operation of theREST based geo-aware content caching service solution of FIG. 2according to some embodiments. As illustrated in FIG. 4, the REST basedgeo-aware content caching service solution can leverage ECM componentsalready exist in an enterprise computing environment 400. That is,content server 450, ACS server 455, storage 457, database 460, BOOSserver 435, program 406, and file system 404 can implement,respectively, content server 350, ACS server 355, storage 357, database360, BOOS server 335, program 306, and file system 304 described above.However, no UCF components are needed. Rather, the ECM components aremodified or otherwise enhanced for communicating and interacting withREST server 420 for DFC services over a RESTful API.

The REST based geo-aware content caching service solution can provideseveral technical advantages. For example, middleware servers (e.g., DFCservers) can horizontally scale with HA support and any clients with anHTTP library can consume the distributed content transfer REST API. Inthis way, a request client can upload content directly to a cachingserver (e.g., BOCS server 435) that is local or geographically theclosest to the request client and no longer has to wait for a contentserver to respond and complete its upload operation. This is anadvantage because it shields the client from the complexity of contentserver operations. Typically, when a request to create a document in acontent management system, the content server has to create a systemobject (e.g., “sysobject”) in a backend repository that will hold themetadata associated with the document (e.g., create a row in arelational database management system). As an example, a sysobject canbe comprised of a set of attributes and a list of contents.

Asynchronously, when the document is transported from the client to thebackend, that document needs to be associated with the object at thebackend repository for various purposes (e.g., versioning, accesscontrolling, etc.). ECM is rich in metadata, all of which have to bemanaged and associated with the document once the document made it tothe content server. The complexity of the content server operations liesin where the document resides in the content server and how the contentserver associates the document with all the metadata (e.g., title,subject, author, keywords, etc.). With the REST based geo-aware contentcaching service solution, all this complexity is decoupled from andopaque to the client.

For example, in FIG. 4, from the perspective of client device 401, allit needs to do to upload a file from file system to 404 is to make aREST API call through program 406 to REST server 420, get an upload URLfrom REST server 420, and upload the file from file system 404 to aserver (e.g., BOCS server 435) through program 406. The client devicedoes not need to know that the server, to which the file is uploaded, isa caching server (e.g., BOCS server 435) that is geographically theclosest to it, or that the caching server, the REST server, and thecontent server work in concert to complete the rest of content upload tothe backend.

FIG. 5 depicts an example of content upload workflow 505 in whichcontent (e.g., a file or document) is uploaded from any HTTP client 501(e.g., client device 501 a, . . . , 501 n, which can include a varietyof user devices such as mobile phones, smart phones, laptop computers,tablet computers, desktop computers, etc., as well as middlewareservers) to content server 550 at backend 510 (e.g., a LAN in enterprisecomputing environment 500) through REST server 520 a (or any server inREST server cluster or middleware 520). The steps enumerated in FIG. 5are as follows:

HTTP client 501 asks REST server 520 a for an ACS/BOCS upload URL, byway of a REST API request (511). In one embodiments, such an upload URLcan refer to an ACS/BOCS upload URL because such an upload operationinvolves BOC server 535 and ACS server 555. As illustrated in FIG. 5, insome embodiments, ACS server is co-located with content server 550 onserver machine 515 to facilitate content transfer to and from storage557 (which is an example of a content repository managed by contentserer 550).

In some embodiments, in response to the REST API request from the HTTPclient, the REST server authenticates the REST API request against thecontent server. The HTTP client provides, in the REST API request,information that the REST server requires to construct an upload URL.Required information may include a network location associated with theclient device (on which the HTTP client is running) and any otherrequired metadata such as the size of the file to be uploaded.Optionally, the client may provide all the necessary metadata for thedocument creation since it may not communicate back to the REST serveragain before the upload completion.

In some embodiments, responsive to the REST API request from HTTP client501, REST server 520 a makes a backend call to obtain a BOOS upload URL(512). Optionally, a network location (e.g., the network locationassociated with the client device) is provided to choose an appropriateadvanced BOOS server. Referring back to FIG. 2, in a distributedenterprise computing environment (e.g., WAN 290), there can be multipleadvanced BOOS servers. Accordingly, when a network location is provided,ACS server 555 may access a database or storage location and retrieve alist of advanced BOOS servers with their corresponding geographicallocations and operate to determine an appropriate BOOS server from themultiple advanced BOOS servers based on the given network location(e.g., by mapping the network location to a BOOS server that isgeographically the closest to the network location), and provide same toREST server 520 a (e.g., a BOOS server that is geographically theclosest to the network location or a list of BOOS servers sorted bytheir respective geographic proximity to the network location). In oneembodiment, ACS server 555 may access a database or storage location andretrieve a list of advanced BOOS servers with their correspondinggeographical locations and provide same to REST server 520 a which, inturn, maps the network location to a BOOS server that is geographicallythe closest to the network location. In some embodiments, REST server520 a can set a timeout condition (e.g., less than 30 seconds) on theprovided upload URL which is used only once.

REST server 520 a then generates or otherwise constructs a response(e.g., an upload link) to respond to the REST API request from HTTPclient 501 (513). The response constructed by REST server 520 a containsthe upload URL. In one embodiment, to comply with the HTTP/1.1, theupload URL is placed in the response “Location” header. In the response,REST server 520 a also puts or embeds a content completion callback URL(referred to hereinafter as the completion URL) in the upload URL as aquery parameter. The completion URL is used by BOOS server 535 to callback to REST server 520 a upon upload completion.

In some embodiments, the completion URL is encrypted so the clientcannot view or modify it. In some embodiments, the REST server returns adocument result in REST format which contains the upload URL.

Once HTTP client 501 has the upload URL from REST server 520 a, ituploads the content to BOOS server 535 using the upload URL (514). Inthis case, no authentication is required. BOOS server 535 is operable tocheck the file size and other necessary metadata integrity. BOOS server535 is also operable decrypt the completion URL in the upload URL andcalls back (e.g., making a REST API call) to REST server 520 a (515).

As discussed above, REST server 520 a may operate in a clusterenvironment and, thus, the REST server node (e.g., REST server 520 a)that makes up the upload URL can be different than the REST server node(e.g., REST server 520 b) that accepts the completion URL. This ispossible because these sessions are stateless—the HTTP client is notrequired to stick to a particular REST server.

In the example of FIG. 5, REST server 520 b accepts the REST API callfrom BOOS server 535 and executes the appropriate inbound operation tocomplete the upload (516). How the user credential is supplied for theinbound operation can be up to the REST server when it creates thecompletion URL and can be opaque to the BOOS server and to the client.The BOOS server response can be consumed by the inbound operationrunning on the REST server that binds the uploaded content with itsassociated document in storage 557 managed by content server 550 (acontent management system).

Once the content is uploaded to the content management system, the RESTserver responds to the BOOS server (517). Optionally, the REST servercreates a new document resource URL and sends it back to the BOOS serverfor confirmation. In turn, the BOOS server responds to the client (518).In one embodiment, BOOS server 535 returns an operation status to clientdevice 501.

Below are example DFC and ACS APIs that support ACS and BOOS contentwrite.

API:

String getACSWriteURL(fileLength, format, networkLocation,completionURLLink, contentURLOptions);

Usage: Get an ACS content write URL for a sysobject. Any generic clientcan make a POST to this URL to import a content file. The sysobject caneither be contentless or contentful at the moment to generate ACS writeURL. It supports to get a BOOS content write URL when the right networklocation is specified. The success of the write URL generation locks thesysobject by the current visitor.

API:

IDfSysObject completeACSWriteURL(InputStream inputStream, intresultIndex);

Usage: Complete the ACS or BOOS content write with the ACS or BOOScompletion request. The input stream is the ACS or BOOS completionrequest body. The success of the write completion unlocks the sysobject.

The new capability of DFC and ACS APIs provides the possibility tointegrate ACS and BOOS write in a REST API. ACS and BOOS content URL isfor anonymous access, with a default expiration duration of, forexample, six hours. The read URL supports HTTP GET method and the writeURL supports HTTP POST method.

Here are some examples:

Content read URL:

http://10.62.87.94:9080/ACS/servlet/ACS?command=read&version=2.3&docbaseid=00000b&basepath=C%3A%5CDocumentum%5Cdata%5CACME01%5Ccontent_storage_01%5C0000000b&filepath=80%5C00%5C37%5Cd7.txt&objectid=0900000b8002de4e&cacheid=dAAEAgA%3D%3D1zcAgA%3D%3D&format=text&pagenum=0&signature=K5qJTOwldcVSzUabfA31%2BdX235Ma74ilItk6ES5cyvT1UR8qqJAOFGJWzhAwSJ1wx2Po7Oh8ZbSFklvOv6BA17wyp4%2BEefAoRcwogYBFSid2BUhj9FLv3CL88egY1np4ut8vPasgxbqYfo6tKOPtUBFZEqwXudBBFVDi5wXJz0c%3D&servername=RESTCS73IRACS1&mode=1&timestamp=1475146131&length=10&mime_type=text%2Fplain&parallel_streaming=true&expire_delta=360

Content write URL:

http://10.62.87.94:9080/ACS/servlet/ACS?command=write&version=2.3&docbaseid=00000b&content_objid=0600000b8000cff6&formatid=2700000b800001d8&storeid=2800000b80000100&store_data=ro0ABXNyADxjb20uZG9jdW1lbnR1bS5mYy5jbGllbnQuY29udGVudC5pbXBsLkNvbnRlbnRTdG9y%0AZXJFeHRyYURhdGH79InsRDaodAwAAHhwc3IAPGNvbS5kb2N1bWVudHVtLmZjLmNsaWVudC5pbXBs%0ALnR5cGVkZGF0YS5EeW5hbWljYWxseVR5cGVkRGF0YQ2yOjPtw7IzDAAAeHIAMWNvbS5kb2N1bWVu%0AdHVtLmZjLmNsaWVudC5pbXBsLnR5cGVkZGF0YS5UeXBlZERhdGFS%2BJtNFLR32QwAAHhyADljb20u%0AZG9jdW1lbnR1bS5mYy5jbGllbnQuaW1wbC50eXBlZGRhdGEuQWJzdHJhY3RUeXBlZERhdGHPXWpF%0AKoIAXQwAAHhwdAAQMDAwMDAwMDAwMDAwMDAwMHcKAAAAAAAAAAAAAXNyADBjb20uZG9jdW1lbnR1%0AbS5mYy5jbGllbnQuaW1wbC50eXBlZGRhdGEuTGl0ZVR5cGVv8Ld%2FWu0npgwAAHhwdXIANFtMY29t%0ALmRvY3VtZW50dW0uZmMuY2xpZW50LmltcGwudHlwZWRkYXRhLkF0dHJpYnV0ZTtORMuIE81SggIA%0AAHhwAAAAAHQAAHNyABFqYXZhLmxhbmcuSW50ZWdlchLioKT3gYc4AgABSQAFdmFsdWV4cgAQamF2%0AYS5sYW5nLk51bWJlcoaslROLl0CLAgAAeHAAAAAAcHBwc3IAEWphdmEubGFuZy5Cb29sZWFuzSBy%0AgNWc%2Bu4CAAFaAAV2YWx1ZXhwAHhzcgATamF2YS51dGlsLkFycmF5TGlzdHiB0h2Zx2GdAwABSQAE%0Ac216ZXhwAAAAAHcEAAAAAHh4eA%3D%3D&partition=0&signature=NFpsoYYoYpUgOgLG31%2FA7ge7SG2VIkuFSZRfx1pxMaJgIK9FfCd3%2FW1RpD9k3Ymukyk5XBjTriOxN7rC%2BZpZZ76%2FkTxZ38DsbNrJuczI%2BzqRx5Zpk%2BE3HA1yvGoXxvAzRmqUj%2FqU5LqCtOnjB1%2FOyszdOOSOQsUasy0A6DAiCgA%3D&servername=RESTCS73IRACS1&mode=2&timestamp=1475146613&length=10&parallel_streaming=true&expire_delta=360

REST API Use Cases

Examples of use cases for BOOS content uploading in a content managementsystem can include the following:

-   -   User Dave wants to create a new contentful document. He creates        the document object using the REST API, but wants to upload a        (large) content file associated with this document via an        adjacent BOOS server asynchronously.    -   User Dave has an existing document. He wants to check in a new        version of, or overwrite the existing content, via an adjacent        BOOS server asynchronously.

The ACS or BOOS content write requires two HTTP calls at the clientside. One REST call is made to the REST server to obtain the contentwrite URL during document creation or checkout. Another HTTP call (anHTTP POST) to the ACS server or the BOOS server to complete the contentupload.

The ACS or BOOS content write URL can be a new link relation. When thereare multiple ACS or BOOS content write URLs, link title can be used todistinguish them.

Non-limiting examples are provided below:

{“rel”:“http://identifiers.company.com/linkrel/distributed- upload”,“title”:“ACS”,“href”:“http://ACS-SERVER:9080/ACS/servlet/ACS?command=write&XXX”}{“rel”:“http://identifiers.company.com/linkrel/distributed- upload”,“title”:“BOCS-Abuja”,“href”:“http://ACS-SERVER:9080/ACS/servlet/BOCS?command=write&XXX”}

Getting an ACS content write URL would lock the sysobject, so GETmethods cannot be used to retrieve the URL. Embodiments may supportretrieving ACS content write URL in below resources:

-   -   Create a new contentless document under folder child documents        resource (RADL>>)    -   Create a new contentless sysobject under folder child objects        resource (RADL>>)    -   Checkout a sysobject resource (RADL>>)

In any of above resources, the sysobject is locked after the ACS or BOOScontent write URL is generated. When the client completes content uploadto the ACS or BOOS server, the sysobject's lock will automatically beremoved.

In some embodiments, new URI query parameters are designed for ACScontent write URL generation. These are provided in Table 1 below.

TABLE 1 Param Data Name Type Description require- boolean Specifieswhether to require distributed content write. It is used dc-write inPOST@FolderChildDocuments Resource, POST@FolderChildObjects Resource,and PUT@Lock Resource. format string Content format for the new contentto upload. Takes effect only when require-dc-write is true. content-long Content length for the new content to upload. Takes effect onlylength when require-dc-write is true. network- string Specifies thedefined network location close to the client geo location location. Itis used to get BOOS content write URL. Takes effect only whenrequire-dc-write is true.

Below are REST samples from the client side to make the requests.

Sample 1—Obtain an ACS write URL during document creation:

------------------------ Request ------------------------ > POST /dctm-rest/repositories/ACME01/folders/0c00000b80001521/documents?Prequire-dc-write=true&format=text&content-length=10 HTTP/1.1 >authorization: Basic ZG1hZG1pbjpwYXNzd29yZA== > Content-Type:application/vnd.company.cs+json;charset=UTF-8 > accept: */* {“properties” : {“object_name”: “testdoc.txt”}}------------------------ Response ------------------------ < StatusCode: 201 < Location: http://localhost:8080/dctm-rest/repositories/ACME01/objects/0900000b8002de4e < Content-Type:application/vnd.company.cs+json;charset=UTF-8  { “name”:“object”,“type”:“dm_document”, “definition”:“http://localhost:8080/dctm-rest/repositories/ACME01/types/dm_document”, “properties”:{“object_name”:“testdoc.txt”, “r_object_type”:“dm_document”, ...,“r_object_id”:“0900000b8002de4e”}, “links”: [{“rel”:“self”,“href”:“xxx”}, ...,{“rel”:“http://identifiers.company.com/linkrel/distributed-upload”,“title”:“ACS”,“href”:“http://BOCS-SERVER?command=write&version=2.3&docbaseid=00000b&content_ objid=0600000b8000parallel_streaming=true&expire_delta=360& completionUrl=aHR0cDovLzEwLjE3MS43NC4yMzo4mVzdC9kYy1jb21wbGV0aW9uP2RjLXRva2VuPVYweE1VRnBRTUZWRVEwNHZjbXREYVdkYVJDczRUM1JZsNVVEVTBlRTE0YWtaTGNYWk5SekUzVTB0TGIxQklTek5qVFhKdlRHNWFVV1p5Ym1oS0wwaElkV2wyYlZWclptVjJWMWcyYzB4dFpHZ3pTVXRvYTFWc1kyWXhjalI0UWpFMlNXTjZZVzExY2pZclVpOTZTRUY2YW14cWJVZFdVa3R3WnowOQ==”}, ... ] }

Sample 2—Obtain ACS write URL during document checkout:

------------------------ Request ------------------------ > PUT /dctm-rest/repositories/ACME01/objects/0900000b8002de4e/lock?require-dc-write=true&format=text&content-length=10 HTTP/1.1 > authorization:Basic ZG1hZG1pbjpwYXNzd29yZA== > accept: */* ------------------------Response ------------------------ < Status Code: 200 < Content-Type:application/vnd.company.cs+json;charset=UTF-8 { “name”:“object”,“type”:“dm_document”, “definition”:“http://localhost:8080/dctm-rest/repositories/ACME01/types/dm_document”, “properties”:{ “objectname”:“testdoc.txt”, “r_object_type”:“dm_document”, ...,“r_object_id”:“0900000b8002de4e”}, “links”: [{“rel”:“self”,“href”:“xxx”}, ..., {“rel”:“http://identifiers.company.com/linkrel/distributed-upload”,“title”:“ACS”,“href”:“http://ACS- SERVER:9080/ACS/servlet/ACS?command=write&version=2.3&docbaseid=00000b&content_objid=0600000b8000cff4&formatid=2700000b800001d8&storeid=2800000b80000100&store_data=rO0ABXNyADxjb20uZG9jdW1lbnR1bS5mYy5jbGllbnQuY29udGVudC5pbXBsLkNvbnRlbnRTdG9y%0AZXJFeHRyYURhdGH79InsRDaodAwAAHhwc3IAPGNvbS5kb2N1bWVudHVtLmZjLmNsaWVudC5pbXBs%0ALnR5cGVkZGF0YS5EeW5hbWljYWxseVR5cGVkRGF0YQ2yOjPtw7IzDAAAeHIAMWNvbS5kb2N1bWVu%0AdHVtLmZjLmNsaW  ...  ] }

Sample 3—Upload content “hello, jo!” to a BOOS server:

------------------------ Request ------------------------ > POSThttp://BOCS-SERVER?command=write&version=2.3&docbaseid=00000b&content_objid=0600000b8000parallel_streaming=true&expire_delta=360&completionUrl=aHR0cDovLzEwLjE3MS43NC4yMzo4mVzdC9kYy1jb21wbGV0aW9uP2RjLXRva2VuPVYweE1VRnBRTUZWRVEwNHZjbXREYVdkYVJDczRUM1JZsNVVEVTBlRTE0YWtaTGNYWk5SekUzVTB0TGIxQklTek5qVFhKdlRHNWFVV1p5Ym1oS0wwaElkV2wyYlZWclptVjJWMWcyYzB4dFpHZ3pTVXRvYTFWc1kyWXhjalI0UWpFMlNXTjZZVzExY2pZclVpOTZTRUY2YW14cWJVZFdVa3R3WnowOQ== HTTP/1.1 > content-type:application/octet-stream hello, jo! ------------------------ Response------------------------ < Status Code: 200

Sample 4—Upload content “hello, jo!” to an ACS server:

------------------------ Request ------------------------ > POSThttp://ACS- SERVER:9080/ACS/servlet/ACS?command=write&xxx HTTP/1.1 >content-type: application/octet-streamcommand=write&version=2.3&docbaseid=00000b&content_objid=0600000b8000cff4&formatid=2700000b800001d8&storeid=2800000b80000100&store_data=rO0ABXNyADxjb20uZG9jdW1lbnR1bS5mYy5jbGllbnQuY29udGVudC5pbXBsLkNvbnRlbnRTdG9y%0AZXJFeHRyYURhdGH79InsRDaodAwAAHhwc3IAPGNvbS5kb2N1bWVudHVtLmZjLmNsaWVudC5pbXBs%0ALnR5cGVkZGF0YS5EeW5hbWljYWxseVR5cGVkRGF0YQ2yOjPtw7IzDAAAeHIAMWNvbS5kb2N1bWVu%0AdHVtLmZjLmNsaWVudC5pbXBsLnR5cGVkZGF0YS5UeXBlZERhdGFS%2BJtNFLR32QwAAHhyADljb20u%0AZG9jdW1lbnR1bS5mYy5jbGllbnQuaW1wbC50eXBlZGRhdGEuQWJzdHJhY3RUeXBlZERhdGHPXWpF%0AKoIAXQwAAHhwdAAQMDAwMDAwMDAwMDAwMDAwMHcKAAAAAAAAAAAAAXNyADBjb20uZG9jdW1lbnR1%0AbS5mYy5jbGllbnQuaW1wbC50eXBlZGRhdGEuTGl0ZVR5cGVv8Ld%2FWu0npgwAAHhwdXIANFtMY29t%0ALmRvY3VtZW50dW0uZmMuY2xpZW50LmltcGwudHlwZWRkYXRhLkF0dHJpYnV0ZTtORMuIE81SggIA%0AAHhwAAAAAHQAAHNyABFqYXZhLmxhbmcuSW50ZWdlchLioKT3gYc4AgABSQAFdmFsdWV4cgAQamF2%0AYS5sYW5nLk51bWJlcoaslR0LlOCLAgAAeHAAAAAAcHBwc3IAEWphdmEubGFuZy5Cb29sZWFuzSBy%0AgNWc%2Bu4CAAFaAAV2YWx1ZXhwAHhzcgATamF2YS51dGlsLkFycmF5TGlzdHiB0h2Zx2GdAwABSQAE%0Ac2l6ZXhwAAAAAHcEAAAAAHh4eA%3D%3D&partition=0&signature=Dmy5ItBxtWCpLULlEK2yrgWFyaY51qUERr3GZb8Mq3%2FrGQDV622n%2F2VQl24srseiXjFAz4J1qquJHXdnmEgV1Dr%2B2BlMXuCHJivC1Ir2JPLtLUoOYq0M2y0TNw58YevpFuJlZ%2F5l4oj%2F%2F0%2F%2BNmnsYMxfN%2FZMlvho4yyYS6aPYk8%3D&servername=RESTCS73IRACS1&mode=2&timestamp=1475146410&length=10&parallel_streaming=true&expire_delta=360&completionUrl=aHR0cDovLzEwLjE3MS43NC4yMzo4MDgwL2RjdG0tcmVzdC9kYy1jb21wbGV0aW9uP2RjLXRva2VuPVYweE1VRnBRTUZWRVEwNHZjbXREYVdkYVJDczRUM1JTUjB0T1FUQmxLM0ZoTVhZMkt6RjVWR1Z3YmpZMU5EVTJjQ3RKTTFBek5ISnZkVXRxWmtWaGFqTkpZVWRPWmxkb0wxWTFTUzlKZDJjNFdWVlVlblZIWlZsSk1GUnNTaXRLVW1abVEwUXhSRWw0VURKV01uWjVkME5KY25GM2NpOXFNRk5MVFVGUFdFbE5TV2hPV1VnM1FYbFpWM0pSTW1sUllrUkZaak5aZVVvM01WUlhkVWhzYVRCT2NrVTRTblIxU2xSdVpHdGFjMVl3V0RSelJteDFabVptTnpsQ1lsWjJOell2VldSMmRFUjNhWEkzYjJaTllXTTNka2R6V1ZOTVduSndha3c0VDNsTmRFUXdMMnROZDNkb2VFcDBSRFZrTUd3MWFFTllVRVYyWjFCaFlqZHpVVFZxZFVsSE5saDVhVEZDZUhRNWVUWm9OV0ZJTjNneFZUbDJMMDlPWlVGSE9GZzBOekJUU21kaU1saHRReloxUlhJcmFsVTROaXRGYldaaFNrNUZRMmwzZVRsWFEyZEtVaXQ0WlRKTk9YTlZjRVpWU0VJNFZEVmlRakJDY1VSemJuaDVhMHhGVFRWMldIRmhPRTQzVGxKV1JXRlNVblUxVlVkblRGSlhTVk5TU1VSSE9UVXlTVkZqVlZOMGFWbHRlVVpzTWpCT2RIWXpTbFJyT0hKSU5HeFpjVmRIWkhoblUxUm5WRGRPTlhKaFZIWkRPRk5FUWxOaWNETXdaazVRUlc4dlZ6aFRiV2Q0VGxkQ1EyVkRlVWxsZWs1MlprWTJhR1FyZFRoalJEUndiRVpWWVcweWQyVkZXRGRCVEhCeVMweERiSEZXV1d4RlFtaDRUMWc0VFU5SlNrUlZZVk5SYVhRM1RIQmlka3RwUWtabWFEQXlNemt6YzJ4WWRqaENNbTlrWkc5WmVHcENWQzkxVEhSNFdEWnVjR0Y2ZEM5VlFYbGtaREZ2UVRsSFZqbEdURXhJS3pRNE1HaHlNMEpZTnpaTlEzQnViRkZ1UVRSS2JqUTNOWEprZWxSVGJFeHdWR0prYUVOSE9YUlJWRU54ZEdsNWVWUm1TSHBSUjJKbk0zcE1NazF1VWxGaVNXcGhNV3RsU2xNeFRteHlSVWwyYzJFeVVXOXJaVUpwYUdvNFUwUkNhRWt4TnpBMVdsRnVlRzkxTkZsNVVEVTBlRTE0YWtaTGNYWk5SekUzVTB0TGIxQklTek5qVFhKdlRHNWFVV1p5Ym1oS0wwaElkV2wyYlZWclptVjJWMWcyYzB4dFpHZ3pTVXRvYTFWc1kyWXhjalI0UWpFMlNXTjZZVzExY2pZclVpOTZTRUY2YW14cWJVZFdVa3R3WnowOQ== hello, jo! ------------------------Response ------------------------ < Status Code: 200

In some cases, an ACS server may require a query string be extractedfrom ACS content write URL and post to the request body, prior to theactual content (e.g., “Hello, jo!”).

By content upload completion, an ACS server, a REST server, and acontent server need to coordinate to complete the document update (see,for example, steps 515, 516, and 517 described above with reference toFIG. 5). As an example, in some embodiments, in steps 512 and 513, theREST server appends a query parameter “completionUrl” to the ACS contentwrite URL. The completionUrl is communicated to the ACS server by theREST client in the ACS content write URL. When the REST client completescontent upload, the ACS server sends ACS completion request to the RESTserver, using this completionUrl. The REST server sends the requestbinary to DFC to complete the post-upload document update. Accordingly,the REST server can expose a new endpoint for the ACS server to send thecompletion request, for example:

POST/dctm-rest/dc-completion?dc-token=XYZ

The URI is for anonymous access from the ACS server, but the parameter“dc-token” contains all the information that the REST server needs todetermine the user credential and document ID. The token is generated bythe REST server and consumed by the REST server only. A non-limitingexample of a dc-token format is provided in FIG. 6. The entirecompletion URL (e.g., the “completionUrl” query parameter) should beencrypted by the REST server and decrypted by the ACS server since it isnot intended to be read and abused by any other entities. In some cases,the “completionUrl” query parameter may be BASE64 encoded in the ACScontent write URL. Other encryption methods may also be used.

FIG. 7 depicts a diagrammatic representation of an example dataprocessing device that may be used to implement a client computingdevice or a server computer in accordance with embodiments disclosedherein. As shown, data processing system 700 may include one or morecentral processing units (CPU) or processors 701 coupled to one or moreuser input/output (I/O) devices 711 and memory devices 703. Examples ofI/O devices 711 may include, but are not limited to, keyboards,displays, monitors, touch screens, printers, electronic pointing devicessuch as mice, trackballs, styluses, touch pads, or the like. Examples ofmemory devices 703 may include, but are not limited to, hard drives(HDs), magnetic disk drives, optical disk drives, magnetic cassettes,tape drives, flash memory cards, random access memories (RAMs),read-only memories (ROMs), smart cards, etc. Data processing system 700can be coupled to display 713, information device 707 and variousperipheral devices (not shown), such as printers, plotters, speakers,etc. through I/O devices 711. Data processing system 700 may also becoupled to external computers or other devices through network interface709, wireless transceiver 705, or other means that is coupled to anetwork such as a LAN, WAN, or the Internet.

ROM, RAM, and HD are computer memories for storing computer-executableinstructions executable by the CPU or capable of being compiled orinterpreted to be executable by the CPU. Suitable computer-executableinstructions may reside on a computer-readable medium (e.g., ROM, RAM,and/or HD), hardware circuitry or the like, or any combination thereof.Within this disclosure, the term “computer-readable medium” is notlimited to ROM, RAM, and HD and can include any type of data storagemedium that can be read by a processor. For example, a computer-readablemedium may refer to a data cartridge, a data backup magnetic tape, afloppy diskette, a flash memory drive, an optical data storage drive, aCD-ROM, ROM, RAM, HD, or the like. The processes described herein may beimplemented in suitable computer-executable instructions that may resideon a computer-readable medium (for example, a disk, CD-ROM, a memory,etc.). Alternatively, the computer-executable instructions may be storedas software code components on a direct access storage device array,magnetic tape, floppy diskette, optical storage device, or otherappropriate computer-readable medium or storage device.

Those skilled in the relevant art will appreciate that the invention canbe implemented or practiced with other computer system configurations,including without limitation multi-processor systems, network devices,mini-computers, mainframe computers, data processors, and the like. Theinvention can be embodied in a computer or data processor that isspecifically programmed, configured, or constructed to perform thefunctions described in detail herein. The invention can also be employedin distributed computing environments, where tasks or modules areperformed by remote processing devices, which are linked through acommunications network such as a LAN, WAN, and/or the Internet. In adistributed computing environment, program modules or subroutines may belocated in both local and remote memory storage devices. These programmodules or subroutines may, for example, be stored or distributed oncomputer-readable media, including magnetic and optically readable andremovable computer discs, stored as firmware in chips, as well asdistributed electronically over the Internet or over other networks(including wireless networks). Example chips may include ElectricallyErasable Programmable Read-Only Memory (EEPROM) chips. Embodimentsdiscussed herein can be implemented in suitable instructions that mayreside on a non-transitory computer-readable medium, hardware circuitryor the like, or any combination and that may be translatable by one ormore server machines. Examples of a non-transitory computer-readablemedium are provided below in this disclosure.

Although the invention has been described with respect to specificembodiments thereof, these embodiments are merely illustrative, and notrestrictive of the invention. Rather, the description is intended todescribe illustrative embodiments, features, and functions in order toprovide a person of ordinary skill in the art context to understand theinvention without limiting the invention to any particularly describedembodiment, feature, or function, including any such embodiment featureor function described in the Abstract or Summary. While specificembodiments of, and examples for, the invention are described herein forillustrative purposes only, various equivalent modifications arepossible within the spirit and scope of the invention, as those skilledin the relevant art will recognize and appreciate. As indicated, thesemodifications may be made to the invention in light of the foregoingdescription of illustrated embodiments of the invention and are to beincluded within the spirit and scope of the invention. Thus, while theinvention has been described herein with reference to particularembodiments thereof, a latitude of modification, various changes andsubstitutions are intended in the foregoing disclosures, and it will beappreciated that in some instances some features of embodiments of theinvention will be employed without a corresponding use of other featureswithout departing from the scope and spirit of the invention as setforth. Therefore, many modifications may be made to adapt a particularsituation or material to the essential scope and spirit of theinvention.

Reference throughout this specification to “one embodiment”, “anembodiment”, or “a specific embodiment” or similar terminology meansthat a particular feature, structure, or characteristic described inconnection with the embodiment is included in at least one embodimentand may not necessarily be present in all embodiments. Thus, respectiveappearances of the phrases “in one embodiment”, “in an embodiment”, or“in a specific embodiment” or similar terminology in various placesthroughout this specification are not necessarily referring to the sameembodiment. Furthermore, the particular features, structures, orcharacteristics of any particular embodiment may be combined in anysuitable manner with one or more other embodiments. It is to beunderstood that other variations and modifications of the embodimentsdescribed and illustrated herein are possible in light of the teachingsherein and are to be considered as part of the spirit and scope of theinvention.

In the description herein, numerous specific details are provided, suchas examples of components and/or methods, to provide a thoroughunderstanding of embodiments of the invention. One skilled in therelevant art will recognize, however, that an embodiment may be able tobe practiced without one or more of the specific details, or with otherapparatus, systems, assemblies, methods, components, materials, parts,and/or the like. In other instances, well-known structures, components,systems, materials, or operations are not specifically shown ordescribed in detail to avoid obscuring aspects of embodiments of theinvention. While the invention may be illustrated by using a particularembodiment, this is not and does not limit the invention to anyparticular embodiment and a person of ordinary skill in the art willrecognize that additional embodiments are readily understandable and area part of this invention.

Any suitable programming language can be used to implement the routines,methods or programs of embodiments of the invention described herein,including C, C++, Java, JavaScript, HTML, or any other programming orscripting code, etc. Other software/hardware/network architectures maybe used. For example, the functions of the disclosed embodiments may beimplemented on one computer or shared/distributed among two or morecomputers in or across a network. Communications between computersimplementing embodiments can be accomplished using any electronic,optical, radio frequency signals, or other suitable methods and tools ofcommunication in compliance with known network protocols.

Different programming techniques can be employed such as procedural orobject oriented. Any particular routine can execute on a single computerprocessing device or multiple computer processing devices, a singlecomputer processor or multiple computer processors. Data may be storedin a single storage medium or distributed through multiple storagemediums, and may reside in a single database or multiple databases (orother data storage techniques). Although the steps, operations, orcomputations may be presented in a specific order, this order may bechanged in different embodiments. In some embodiments, to the extentmultiple steps are shown as sequential in this specification, somecombination of such steps in alternative embodiments may be performed atthe same time. The sequence of operations described herein can beinterrupted, suspended, or otherwise controlled by another process, suchas an operating system, kernel, etc. The routines can operate in anoperating system environment or as stand-alone routines. Functions,routines, methods, steps, and operations described herein can beperformed in hardware, software, firmware, or any combination thereof.

Embodiments described herein can be implemented in the form of controllogic in software or hardware or a combination of both. The controllogic may be stored in an information storage medium, such as acomputer-readable medium, as a plurality of instructions adapted todirect an information processing device to perform a set of stepsdisclosed in the various embodiments. Based on the disclosure andteachings provided herein, a person of ordinary skill in the art willappreciate other ways and/or methods to implement the invention.

It is also within the spirit and scope of the invention to implement insoftware programming or code any of the steps, operations, methods,routines or portions thereof described herein, where such softwareprogramming or code can be stored in a computer-readable medium and canbe operated on by a processor to permit a computer to perform any of thesteps, operations, methods, routines or portions thereof describedherein. In general, the functions of the invention can be achieved by,for example, distributed, or networked systems, components, andcircuits. In another example, communication or transfer (or otherwisemoving from one place to another) of data may be wired, wireless, or byany other means.

A “computer-readable medium” may be any medium that can contain, store,communicate, propagate, or transport the program for use by or inconnection with the instruction execution system, apparatus, system, ordevice. The computer-readable medium can be, by way of example only butnot by limitation, an electronic, magnetic, optical, electromagnetic,infrared, or semiconductor system, apparatus, system, device,propagation medium, or computer memory. Such computer-readable mediumshall generally be machine readable and include software programming orcode that can be human readable (e.g., source code) or machine readable(e.g., object code). Examples of non-transitory computer-readable mediacan include random access memories, read-only memories, hard drives,data cartridges, magnetic tapes, floppy diskettes, flash memory drives,optical data storage devices, compact-disc read-only memories, and otherappropriate computer memories and data storage devices. In anillustrative embodiment, some or all of the software components mayreside on a single server computer or on any combination of separateserver computers. As one skilled in the art can appreciate, a computerprogram product implementing an embodiment disclosed herein may compriseone or more non-transitory computer-readable media storing computerinstructions translatable by one or more processors in a computingenvironment.

As used herein, the term “document” refers broadly to any data,including managed content objects. Example documents may include,without limitation, spreadsheets, source code, electronic slideshows,digital images, word processor documents, text files, digital videos,digital audio recordings, e-mails, digital calendar entries, etc.

It will also be appreciated that one or more of the elements depicted inthe drawings/figures can be implemented in a more separated orintegrated manner, or even removed or rendered as inoperable in certaincases, as is useful in accordance with a particular application.Additionally, any signal arrows in the drawings/figures should beconsidered only as exemplary, and not limiting, unless otherwisespecifically noted.

As used herein, the terms “comprises,” “comprising,” “includes,”“including,” “has,” “having,” or any other variation thereof, areintended to cover a non-exclusive inclusion. For example, a process,product, article, or apparatus that comprises a list of elements is notnecessarily limited to only those elements but may include otherelements not expressly listed or inherent to such process, product,article, or apparatus.

Furthermore, the term “or” as used herein is generally intended to mean“and/or” unless otherwise indicated. For example, a condition A or B issatisfied by any one of the following: A is true (or present) and B isfalse (or not present), A is false (or not present) and B is true (orpresent), and both A and B are true (or present). As used herein,including the claims that follow, a term preceded by “a” or “an” (and“the” when antecedent basis is “a” or “an”) includes both singular andplural of such term, unless clearly indicated within the claim otherwise(i.e., that the reference “a” or “an” clearly indicates only thesingular or only the plural). Also, as used in the description hereinand throughout the claims that follow, the meaning of “in” includes “in”and “on” unless the context clearly dictates otherwise. The scope of thepresent disclosure should be determined by the following claims andtheir legal equivalents.

What is claimed is:
 1. A method for geo-aware content transfer,comprising: receiving, by a server computer, a representational statetransfer (REST) application programming interface (API) request from aclient device for an upload link, the REST API request containing anetwork location associated with the client device; obtaining, by theserver computer using the network location associated with the clientdevice, a upload universal resource locator (URL) targeting a cachingserver that is geographically closest to the network location associatedwith the client device; constructing, by the server computer, an uploadlink containing the upload URL and a completion callback parameter;sending the upload link to the client device, wherein the client deviceuses the upload URL in the upload link constructed by the servercomputer to upload content to the caching server and, in response, thecaching server interprets the completion callback parameter in theupload link to obtain a completion URL targeting the server computerand, upon completion of the uploading of the content from the clientdevice, makes a REST API call to the server computer using thecompletion URL; responsive to the REST API call by the caching server,executing, by the server computer or another server computer in acluster with the server computer, an inbound operation to complete theuploading of the content to a content management system, the inboundoperation including associating the content with a content URL in thecontent management system; and returning the content URL to the cachingserver, the returning performed by the server computer, wherein thecaching server sends the content URL to the client device.
 2. The methodaccording to claim 1, wherein the obtaining comprises sending, by theserver computer, the network location associated with the client deviceto an accelerated content services (ACS) server, wherein the ACS serveris co-located with the content management system on a server machine,and wherein the ACS server is operable to determine the upload URL basedon the network location associated with the client device and return theupload URL to the server computer.
 3. The method according to claim 1,wherein the upload URL is one of a plurality of upload URLs determinedby an accelerated content services (ACS) server co-located with thecontent management system on a server machine, and wherein the servercomputer is operable to determine the upload URL from the plurality ofupload URLs determined by the ACS server.
 4. The method according toclaim 1, wherein the REST API request from the client device contains afile size for the content and wherein the caching server is configuredfor verifying the file size.
 5. The method according to claim 1, whereinthe completion callback parameter is encrypted in the upload linkconstructed by the server computer so that the client device cannot viewor modify the completion callback parameter.
 6. The method according toclaim 1, wherein the server computer is communicatively connected to theclient device and the caching server over a wide area network in anenterprise computing environment and to the content management systemover a local area network in the enterprise computing environment. 7.The method according to claim 1, wherein the content URL associates thecontent with a file in the content management system.
 8. A system forgeo-aware content transfer, comprising: a processor; a non-transitorycomputer-readable medium; and stored instructions translatable by theprocessor to perform: receiving a representational state transfer (REST)application programming interface (API) request from a client device foran upload link, the REST API request containing a network locationassociated with the client device; obtaining, using the network locationassociated with the client device, a upload universal resource locator(URL) targeting a caching server that is geographically closest to thenetwork location associated with the client device; constructing anupload link containing the upload URL and a completion callbackparameter; sending the upload link to the client device, wherein theclient device uses the upload URL in the upload link to upload contentto the caching server and, in response, the caching server interpretsthe completion callback parameter in the upload link to obtain acompletion URL and, upon completion of the uploading of the content fromthe client device, makes a REST API call using the completion URL;responsive to the REST API call by the caching server, executing aninbound operation to complete the uploading of the content to a contentmanagement system, the inbound operation including associating thecontent with a content URL in the content management system; andreturning the content URL to the caching server which sends the contentURL to the client device.
 9. The system of claim 8, wherein theobtaining comprises sending the network location associated with theclient device to an accelerated content services (ACS) server, whereinthe ACS server is co-located with the content management system on aserver machine, and wherein the ACS server is operable to determine theupload URL based on the network location associated with the clientdevice.
 10. The system of claim 8, wherein the upload URL is one of aplurality of upload URLs determined by an accelerated content services(ACS) server co-located with the content management system on a servermachine, and wherein the stored instructions are further translatable bythe processor to perform determining the upload URL from the pluralityof upload URLs determined by the ACS server.
 11. The system of claim 8,wherein the REST API request from the client device contains a file sizefor the content and wherein the caching server is configured forverifying the file size.
 12. The system of claim 8, wherein thecompletion callback parameter is encrypted in the upload link so thatthe client device cannot view or modify the completion callbackparameter.
 13. The system of claim 8, wherein the processor iscommunicatively connected to the client device and the caching serverover a wide area network in an enterprise computing environment and tothe content management system over a local area network in theenterprise computing environment.
 14. The system of claim 8, wherein thecontent URL associates the content with a file in the content managementsystem.
 15. A computer program product for geo-aware content transfer,the computer program product comprising a non-transitorycomputer-readable medium storing instructions translatable by a servercomputer to perform: receiving a representational state transfer (REST)application programming interface (API) request from a client device foran upload link, the REST API request containing a network locationassociated with the client device; obtaining, using the network locationassociated with the client device, a upload universal resource locator(URL) targeting a caching server that is geographically closest to thenetwork location associated with the client device; constructing anupload link containing the upload URL and a completion callbackparameter; sending the upload link to the client device, wherein theclient device uses the upload URL in the upload link to upload contentto the caching server and, in response, the caching server interpretsthe completion callback parameter in the upload link to obtain acompletion URL and, upon completion of the uploading of the content fromthe client device, makes a REST API call using the completion URL;responsive to the REST API call by the caching server, executing aninbound operation to complete the uploading of the content to a contentmanagement system, the inbound operation including associating thecontent with a content URL in the content management system; andreturning the content URL to the caching server which sends the contentURL to the client device.
 16. The computer program product of claim 15,wherein the obtaining comprises sending the network location associatedwith the client device to an accelerated content services (ACS) server,wherein the ACS server is co-located with the content management systemon a server machine, and wherein the ACS server is operable to determinethe upload URL based on the network location associated with the clientdevice and return the upload URL to the server computer.
 17. Thecomputer program product of claim 15, wherein the upload URL is one of aplurality of upload URLs determined by an accelerated content services(ACS) server co-located with the content management system on a servermachine, and wherein the instructions are further translatable by theserver computer to perform determining the upload URL from the pluralityof upload URLs determined by the ACS server.
 18. The computer programproduct of claim 15, wherein the REST API request from the client devicecontains a file size for the content and wherein the caching server isconfigured for verifying the file size.
 19. The computer program productof claim 15, wherein the completion callback parameter is encrypted inthe upload link so that the client device cannot view or modify thecompletion callback parameter.
 20. The computer program product of claim15, wherein the server computer is communicatively connected to theclient device and the caching server over a wide area network in anenterprise computing environment and to the content management systemover a local area network in the enterprise computing environment.